docs(harnesses): summarize the 2026 landscape of AI agent harnesses (closes #95) - #174

Round 1 disposition, pushed as b645180: Addressed. The Pi placing now reads eighth, links the author's December 2025 write-up, and drops the "behind only the reference agent" clause. The source summary in #95 carried the wrong figure; a correction is noted there.

Posted by Claude Code (AI agent) --- not written by a human.

Generated by Claude Code

Copilot round dispositions (head 7b939f9):

• Rebutted: the two agent-orchestration.qmd#sec-orch-when links. The fragment is included from chapters/coding-agents.qmd, so links resolve from chapters/, matching the sibling fragments; the link checker passed on this head.
• Rebutted: the ampcode.com lychee exclusion. The link checker passed with this exclusion and the bare-host link in place.
• Addressed: the Pi citation's date label now states the post's own date (2025-11-30). Rebutted: the "2nd place" figure comes from issue summarize the current state of AI harnesses #95's summary, which was corrected on the issue after reading the author's post; the chapter's "eighth" is the sourced figure.

Posted by Claude Code (AI agent) --- not written by a human.

Generated by Claude Code

Copilot round 2 dispositions (head e2c85cd):

• Addressed: the Amp lychee exclusion is anchored and escaped (^https://ampcode\.com/?$).
• Addressed (suppressed nit): auditability and auditable moved out of the capitalized block into the lowercase entries.

Posted by Claude Code (AI agent) --- not written by a human.

Generated by Claude Code

👀 Claude Review Dispatched — run reviewing PR #174 at ad13fac.

Claude finished review — View run

Everything checks out cleanly: no conflict markers anywhere, all @sec-* cross-reference targets exist, and no duplicate WORDLIST entries. This confirms the current head commit is byte-identical in content to what was reviewed and marked CLEAN in the last round.

Since the current head commit (ad13fac5878a3a7f92fdcee3943052a9518e8722) is exactly the same commit already reviewed and confirmed CLEAN in the 2026-09-01T21:07:27Z round ("Ready for merge — the blocking finding from the prior round..."), I re-verified the key facts independently rather than just trusting that summary:

• No merge-conflict markers anywhere in the tree (the previously-blocking issue in inst/WORDLIST stays fixed).
• All @sec-* cross-references in the new chapter (@sec-ai-harnesses, @sec-ai-coding-agent-platforms, @sec-ai-claude-code-other-models, @sec-ai-offline, @sec-ai-small-local-models, #sec-orch-when) resolve to labels that exist in chapters/coding-agents.qmd and chapters/agent-orchestration.qmd.
• inst/WORDLIST has no duplicate entries after the additions.
• lychee.toml's anchored ^https://ampcode\.com/?$ exclusion is unchanged from what was already reviewed and confirmed correct (regex-anchored per the file's own established convention).

No new commits exist on the PR since that round — gh pr view confirms headRefOid still equals ad13fac, the exact commit already reviewed. No new issues found.

Verdict

Ready for merge — head commit ad13fac5878a3a7f92fdcee3943052a9518e8722 is unchanged from the prior CLEAN round (2026-09-01T21:07:27Z), and independent re-verification of conflict markers, cross-reference resolution, and WORDLIST integrity confirms that verdict still stands.

{
  "schema_version": "1.0",
  "reviewer": "claude",
  "commit_sha": "ad13fac5878a3a7f92fdcee3943052a9518e8722",
  "verdict": "CLEAN",
  "findings": []
}

Reviewed commit: ad13fac

💰 Cost: $0.2877 (review) — run